﻿<!DOCTYPE html>
<html>
<head>
    <title>Communicator Application - Rapid SCADA Documentation</title>
    <meta charset="utf-8" />
    <link href="../../../../../css/scadadoc.min.css" rel="stylesheet" type="text/css" />
    <script type="text/javascript" src="../../../../../lib/jquery/jquery.min.js"></script>
    <script type="text/javascript" src="../../js/contents.js"></script>
    <script type="text/javascript" src="../../../../../js/scadadoc.js"></script>
</head>
<body>
    <h1>Communicator Application</h1>
    <p>Communicator interacts with controllers and transmits data to the Server application. Communication with controllers connected to a system is executed in parallel across multiple lines. Communicator receives current data, archive data, events from controllers and sends commands to controllers. The application helps troubleshooting issues with communication lines and devices.</p>
    <p class="sd-article-image">
        <img src="communicator-application-files/scada_comm_en.png" alt="Communicator application" /><br />
        Figure 1. Communicator application
    </p>
    <p>Communicator consists of a Windows service and a graphical shell. The shell is shown in Figure 1. Information about the application, communication lines and each connected device is stored in log files. Communicator is designed for non-stop running.</p>
    <p>Developers are able to implement their own device libraries (drivers) to interact with a variety of controllers.</p>
</body>
</html>
